Awesome, thanks a lot! I merged that right away, and will make it part of the final 1.5 release.

Don't forget to update version in pom.xml before tagging
A checkout of the 1.5 tag should have a pom.xml with version 1.5
Then, on the master branch, you should update it to version 1.5.1-SNAPSHOT (or 1.6-SNAPSHOT depending on your roadmap).

Aha, I see!

So, when someone syncs to tag 1.5, the pom.xml should use "1.5" as the version.
Then, further on in development, it should be "1.5.1-SNAPSHOT" (for example), until I tag "1.5.1".

Right?

You got it.
And if you were to use maven as your build tool, this would be done
automatically (version change in pom & git tagging).
When apache flex devs will have progressed on maven usability, I think
you will be able to consider that switch :)

Le 30/04/2014 11:42, Daniel Sperl a écrit :

Aha, I see!

So, when someone syncs to tag 1.5, the pom.xml should use "1.5" as the
version.
Then, further on in development, it should be "1.5.1-SNAPSHOT" (for
example), until I tag "1.5.1".

Right?

—
Reply to this email directly or view it on GitHub
#535 (comment).

Perfect, that will be manageable! =)
Merci beaucoup, Simon!

@morvans greetings! I see you're familiar with Maven builds. Could you comment something on this http://stackoverflow.com/questions/24107287/error-flex-compiler-and-flex-framework-versions-doesnt-match-compiler-x?